Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fda1c4524c2c9285eebbd344f3e3cc60907984004369a7d293de59c2c9d8a729

Tx prefix hash: b1bfde3b56523d94f5d3734151fb9b81753589d13c8bc3e40f9d8b8eae364ae4
Tx public key: 695b3a5f1dafa198fe40141c859e4d221d29026bb792816d65105aadcbd3aa70
Timestamp: 1673456090 Timestamp [UCT]: 2023-01-11 16:54:50 Age [y:d:h:m:s]: 02:095:20:19:06
Block: 672543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590185 RingCT/type: yes/0
Extra: 01695b3a5f1dafa198fe40141c859e4d221d29026bb792816d65105aadcbd3aa7002110000000a52542ceb000000000000000000

1 output(s) for total of 3.627319483000 dcy

stealth address amount amount idx
00: 39ac389c7bab0ea0292f7ced17d93beb9c4a45b51a5254178db02fad5a4ca206 3.627319483000 1114100 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 672553, "vin": [ { "gen": { "height": 672543 } } ], "vout": [ { "amount": 3627319483, "target": { "key": "39ac389c7bab0ea0292f7ced17d93beb9c4a45b51a5254178db02fad5a4ca206" } } ], "extra": [ 1, 105, 91, 58, 95, 29, 175, 161, 152, 254, 64, 20, 28, 133, 158, 77, 34, 29, 41, 2, 107, 183, 146, 129, 109, 101, 16, 90, 173, 203, 211, 170, 112, 2, 17, 0, 0, 0, 10, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8