Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f9d7d1cdd3e603ed7e90c519a0bc033ef0b191f282b452d1ded4f9121f6809

Tx prefix hash: 0a27c4f4f23cba025c5c42789bec89b3c311a88f9479ab868748b46a945ea14f
Tx public key: d7298057636ebd7dbb72cd7f6df427afdb0bfd0f59d3a4bcc16bd2e4f740bd43
Timestamp: 1698514930 Timestamp [UCT]: 2023-10-28 17:42:10 Age [y:d:h:m:s]: 01:227:20:42:35
Block: 879653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423855 RingCT/type: yes/0
Extra: 01d7298057636ebd7dbb72cd7f6df427afdb0bfd0f59d3a4bcc16bd2e4f740bd4302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.747041043000 dcy

stealth address amount amount idx
00: 4a30d6e3b6a11522b32845e9606147bed56ab8327c8a90c550fca4a02f70253d 0.747041043000 1335187 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": 879663, "vin": [ { "gen": { "height": 879653 } } ], "vout": [ { "amount": 747041043, "target": { "key": "4a30d6e3b6a11522b32845e9606147bed56ab8327c8a90c550fca4a02f70253d" } } ], "extra": [ 1, 215, 41, 128, 87, 99, 110, 189, 125, 187, 114, 205, 127, 109, 244, 39, 175, 219, 11, 253, 15, 89, 211, 164, 188, 193, 107, 210, 228, 247, 64, 189, 67, 2, 17, 0, 0, 0, 1, 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