Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5778c2e907264c45c7025c2e010ff42488626060a2843cb95e1cb259f15c38a

Tx prefix hash: cc4eb1dd09adfc5f7c7222aefd7db50139240fffe0c3a0e8ed72dca72784b373
Tx public key: 469040b3f4edf9fee7816e7590b54d2857c0dca91f38c52d9646ad9076d5d795
Timestamp: 1731249879 Timestamp [UCT]: 2024-11-10 14:44:39 Age [y:d:h:m:s]: 00:135:15:32:14
Block: 1150740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96745 RingCT/type: yes/0
Extra: 01469040b3f4edf9fee7816e7590b54d2857c0dca91f38c52d9646ad9076d5d79502110000000bdfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651757f4265c82292906561efac07d4eb99a5837c9e7ec9dc4ea1fe92ac7a17e 0.600000000000 1636123 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": 1150750, "vin": [ { "gen": { "height": 1150740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651757f4265c82292906561efac07d4eb99a5837c9e7ec9dc4ea1fe92ac7a17e" } } ], "extra": [ 1, 70, 144, 64, 179, 244, 237, 249, 254, 231, 129, 110, 117, 144, 181, 77, 40, 87, 192, 220, 169, 31, 56, 197, 45, 150, 70, 173, 144, 118, 213, 215, 149, 2, 17, 0, 0, 0, 11, 223, 195, 186, 73, 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