Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5664bf3ed02fdeede2ae973c33409d5381bdeecd4a66f6eadaaf1c60f5d5b4

Tx prefix hash: b11d08dcff551003242df0b7bf911e31fa38066f4d980612a62fdf0b525a5346
Tx public key: b29942bd89d0f83699328dec72866b03a90b2ac65e9179e595b14d23e50b727f
Timestamp: 1713050200 Timestamp [UCT]: 2024-04-13 23:16:40 Age [y:d:h:m:s]: 01:236:22:44:08
Block: 999913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428063 RingCT/type: yes/0
Extra: 01b29942bd89d0f83699328dec72866b03a90b2ac65e9179e595b14d23e50b727f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb61d5f3412cf7011d11f9b016bb22aa2c548aafd934765cec590949045bf43f 0.600000000000 1460401 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": 999923, "vin": [ { "gen": { "height": 999913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb61d5f3412cf7011d11f9b016bb22aa2c548aafd934765cec590949045bf43f" } } ], "extra": [ 1, 178, 153, 66, 189, 137, 208, 248, 54, 153, 50, 141, 236, 114, 134, 107, 3, 169, 11, 42, 198, 94, 145, 121, 229, 149, 177, 77, 35, 229, 11, 114, 127, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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