Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140878bd95576df39886a8912a03dbed26b044bcd4f94502ca8c8a37872d8d12

Tx prefix hash: d1d44eaa0c5778a3cf317033f5a666e9ea826ef9e97e76ff2e0e62aa6d774075
Tx public key: bfca9a27aff3c43a1d67e821d39e902d6980886c2bd384890fba366a68e37f4d
Timestamp: 1754527758 Timestamp [UCT]: 2025-08-07 00:49:18 Age [y:d:h:m:s]: 00:105:07:12:11
Block: 1341809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74298 RingCT/type: yes/0
Extra: 01bfca9a27aff3c43a1d67e821d39e902d6980886c2bd384890fba366a68e37f4d021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e32b47e9eb92fc7fec6dc993f1df9fbe07d53263f75b342451087a512140e38 0.600000000000 1829636 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": 1341819, "vin": [ { "gen": { "height": 1341809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e32b47e9eb92fc7fec6dc993f1df9fbe07d53263f75b342451087a512140e38" } } ], "extra": [ 1, 191, 202, 154, 39, 175, 243, 196, 58, 29, 103, 232, 33, 211, 158, 144, 45, 105, 128, 136, 108, 43, 211, 132, 137, 15, 186, 54, 106, 104, 227, 127, 77, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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