Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77dd21f0195528481a597cb3a303a5e7f1603cd2df2d98e6199db4c9fab51f9

Tx prefix hash: 7f1aa9a7248f970c31ba9e09fbe6806b0f0d38060f1291f301893bb461be9121
Tx public key: 45d3a6bb3534330000f83ef7e03764996fefb3d5d04eaebac557e95bbcf16e4a
Timestamp: 1718532593 Timestamp [UCT]: 2024-06-16 10:09:53 Age [y:d:h:m:s]: 00:274:20:28:30
Block: 1045411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196386 RingCT/type: yes/0
Extra: 0145d3a6bb3534330000f83ef7e03764996fefb3d5d04eaebac557e95bbcf16e4a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f464bf51ff2b2a1482d7f08b66a7081dc31f1f69c1d702af9581bd74c6503a 0.600000000000 1514974 of 15

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": 1045421, "vin": [ { "gen": { "height": 1045411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f464bf51ff2b2a1482d7f08b66a7081dc31f1f69c1d702af9581bd74c6503a" } } ], "extra": [ 1, 69, 211, 166, 187, 53, 52, 51, 0, 0, 248, 62, 247, 224, 55, 100, 153, 111, 239, 179, 213, 208, 78, 174, 186, 197, 87, 233, 91, 188, 241, 110, 74, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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