Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce272c969cfff2f5b1adec1b0a1a0ddd1d071839c9513a7c7a0637339f0feb23

Tx prefix hash: ef242251512039b7e898535dade5b837a58ad067f3df10e2549dad97484746a1
Tx public key: 2e66bdd0de78333863bcac12b85f6c9d565e3f3e0fe3f19fa174f3026e371c11
Timestamp: 1699845109 Timestamp [UCT]: 2023-11-13 03:11:49 Age [y:d:h:m:s]: 01:361:14:13:53
Block: 890466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517327 RingCT/type: yes/0
Extra: 012e66bdd0de78333863bcac12b85f6c9d565e3f3e0fe3f19fa174f3026e371c1102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.687886030000 dcy

stealth address amount amount idx
00: 18a19a435dcd97fb6a137014d663ebcc35750f881394cb8129862b0a31253f85 0.687886030000 1346489 of 0

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": 890476, "vin": [ { "gen": { "height": 890466 } } ], "vout": [ { "amount": 687886030, "target": { "key": "18a19a435dcd97fb6a137014d663ebcc35750f881394cb8129862b0a31253f85" } } ], "extra": [ 1, 46, 102, 189, 208, 222, 120, 51, 56, 99, 188, 172, 18, 184, 95, 108, 157, 86, 94, 63, 62, 15, 227, 241, 159, 161, 116, 243, 2, 110, 55, 28, 17, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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