Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 926ec80852435ef622bda03d32db07c99eb7fe9edd1e3b0857553d3c454c44d6

Tx prefix hash: 4550f92660c57db3bef0b00c87e7c8940585095470dcc390a6a034797d2a2fa5
Tx public key: 5b2e3a243e8c863105b2ce3cd80e35e01445e2d87962e5883d9988361d753995
Timestamp: 1729725161 Timestamp [UCT]: 2024-10-23 23:12:41 Age [y:d:h:m:s]: 00:139:19:15:47
Block: 1138152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99710 RingCT/type: yes/0
Extra: 015b2e3a243e8c863105b2ce3cd80e35e01445e2d87962e5883d9988361d7539950211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efd75c8b19afaf9dfca4905c164382876e3fd22780fae9a1f65bb463e4e5b65e 0.600000000000 1621767 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": 1138162, "vin": [ { "gen": { "height": 1138152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efd75c8b19afaf9dfca4905c164382876e3fd22780fae9a1f65bb463e4e5b65e" } } ], "extra": [ 1, 91, 46, 58, 36, 62, 140, 134, 49, 5, 178, 206, 60, 216, 14, 53, 224, 20, 69, 226, 216, 121, 98, 229, 136, 61, 153, 136, 54, 29, 117, 57, 149, 2, 17, 0, 0, 0, 2, 31, 10, 83, 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