Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3417e320c356b0639606c1c7371a7a212318bfb3215356d113a32cd222869059

Tx prefix hash: c63e7e45deb451d68bdd671bfef713ce455327b720e52b2e12514df3a8a21bad
Tx public key: 6cd56baad8805d85f26cad9d900bc0f3229aa796cffe5b1be66c2e3201b8c0e4
Timestamp: 1721643709 Timestamp [UCT]: 2024-07-22 10:21:49 Age [y:d:h:m:s]: 00:303:16:00:30
Block: 1071180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216998 RingCT/type: yes/0
Extra: 016cd56baad8805d85f26cad9d900bc0f3229aa796cffe5b1be66c2e3201b8c0e402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 082e7aa0dcfa84cca6f0b2b31635ef507f245c803e117a2dc9e9dc152f2d454e 0.600000000000 1543303 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": 1071190, "vin": [ { "gen": { "height": 1071180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "082e7aa0dcfa84cca6f0b2b31635ef507f245c803e117a2dc9e9dc152f2d454e" } } ], "extra": [ 1, 108, 213, 107, 170, 216, 128, 93, 133, 242, 108, 173, 157, 144, 11, 192, 243, 34, 154, 167, 150, 207, 254, 91, 27, 230, 108, 46, 50, 1, 184, 192, 228, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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