Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc9b42a26f14a5b49e06ca2469757da1450f1f5406e2b85fae2b91873d9044d

Tx prefix hash: 5506135acc41df1f198d7731bed8daa39c0a00268248bb014360b93ad4a4e1ba
Tx public key: fefa6335c7e935c4097bedb5e813c55349b22491e6b7b58fb04ea4c377c1bc0e
Timestamp: 1716119012 Timestamp [UCT]: 2024-05-19 11:43:32 Age [y:d:h:m:s]: 00:157:02:53:12
Block: 1025388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112501 RingCT/type: yes/0
Extra: 01fefa6335c7e935c4097bedb5e813c55349b22491e6b7b58fb04ea4c377c1bc0e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 470ef2e4226b5349edeb2669ac36d689da83f18314943ad8db6a7ad547db5728 0.600000000000 1491853 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": 1025398, "vin": [ { "gen": { "height": 1025388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "470ef2e4226b5349edeb2669ac36d689da83f18314943ad8db6a7ad547db5728" } } ], "extra": [ 1, 254, 250, 99, 53, 199, 233, 53, 196, 9, 123, 237, 181, 232, 19, 197, 83, 73, 178, 36, 145, 230, 183, 181, 143, 176, 78, 164, 195, 119, 193, 188, 14, 2, 17, 0, 0, 0, 3, 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