Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00af95ba9a2ce20ad52bad170245dd8093e538569a933f24816df6285fb7f10

Tx prefix hash: 54249d9ae6807204cdb9dfc5507a7351183b55d4e81bc79a80eb2eb63993e793
Tx public key: 180850dc58df1a3a17dbbb46e6cba1fb1b81309379c9e3c4132947a64365a845
Timestamp: 1746929241 Timestamp [UCT]: 2025-05-11 02:07:21 Age [y:d:h:m:s]: 00:190:19:20:48
Block: 1280280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134079 RingCT/type: yes/0
Extra: 01180850dc58df1a3a17dbbb46e6cba1fb1b81309379c9e3c4132947a64365a8450211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57ad606a31b6b3db42c154e773a5c34ead023c26bb961ccd3775d5cfa8b326e9 0.600000000000 1767663 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": 1280290, "vin": [ { "gen": { "height": 1280280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57ad606a31b6b3db42c154e773a5c34ead023c26bb961ccd3775d5cfa8b326e9" } } ], "extra": [ 1, 24, 8, 80, 220, 88, 223, 26, 58, 23, 219, 187, 70, 230, 203, 161, 251, 27, 129, 48, 147, 121, 201, 227, 196, 19, 41, 71, 166, 67, 101, 168, 69, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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