Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1542354f056937c8ffb02bfa81588f70bce4209a322ff08a5dbceef266afebd8

Tx prefix hash: 3efc85cce4c8e8fd87e634181cc28e7ce83a4c8e0f44f437160a10e7addc0575
Tx public key: fc40516a482521a80007cd9ea4176fceefdba87b0a5c8deb1a040e07944d93af
Timestamp: 1739916025 Timestamp [UCT]: 2025-02-18 22:00:25 Age [y:d:h:m:s]: 00:231:06:56:52
Block: 1222205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163011 RingCT/type: yes/0
Extra: 01fc40516a482521a80007cd9ea4176fceefdba87b0a5c8deb1a040e07944d93af0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6e8d8b09e696f13e3d84e46eae5953b0bca7745a069dd8f8a68a8ae72acd1cf 0.600000000000 1709056 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": 1222215, "vin": [ { "gen": { "height": 1222205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6e8d8b09e696f13e3d84e46eae5953b0bca7745a069dd8f8a68a8ae72acd1cf" } } ], "extra": [ 1, 252, 64, 81, 106, 72, 37, 33, 168, 0, 7, 205, 158, 164, 23, 111, 206, 239, 219, 168, 123, 10, 92, 141, 235, 26, 4, 14, 7, 148, 77, 147, 175, 2, 17, 0, 0, 0, 4, 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