Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c52c797dca1851973673e2caf97bba79ca65894296ea445dcfc2761ac3449b4

Tx prefix hash: c2f003b56a08b821435fe28cef7e7c25ec49d93c51409b48f9a7efc680ea852a
Tx public key: 3d5c3bdf68e8aef9e21bf3062f398e920ad1ceb9518ff702e523affacd3c7a28
Timestamp: 1647642186 Timestamp [UCT]: 2022-03-18 22:23:06 Age [y:d:h:m:s]: 02:240:13:14:49
Block: 461388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 691401 RingCT/type: yes/0
Extra: 013d5c3bdf68e8aef9e21bf3062f398e920ad1ceb9518ff702e523affacd3c7a28021100000001bf7ee4e7000000000000000000

1 output(s) for total of 18.166606043000 dcy

stealth address amount amount idx
00: 1357d24954794c14b44060ae4151c2f2231ca66b87662b21f70212964a7a69b8 18.166606043000 878617 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": 461398, "vin": [ { "gen": { "height": 461388 } } ], "vout": [ { "amount": 18166606043, "target": { "key": "1357d24954794c14b44060ae4151c2f2231ca66b87662b21f70212964a7a69b8" } } ], "extra": [ 1, 61, 92, 59, 223, 104, 232, 174, 249, 226, 27, 243, 6, 47, 57, 142, 146, 10, 209, 206, 185, 81, 143, 247, 2, 229, 35, 175, 250, 205, 60, 122, 40, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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