Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac1eceea8dc72449cd7cb4de4e73a0f000c5debca5a1aa559de3fb3517b21632

Tx prefix hash: 823425fcf8145d7d512a7e50e1a5b93adbfbd68366eae5615c45f52b254396a1
Tx public key: 26ddcad68c561b8b9bcce9314ccb33348276328bfc533172e69c79e9ecf72fce
Timestamp: 1731515820 Timestamp [UCT]: 2024-11-13 16:37:00 Age [y:d:h:m:s]: 00:142:06:15:51
Block: 1152935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101493 RingCT/type: yes/0
Extra: 0126ddcad68c561b8b9bcce9314ccb33348276328bfc533172e69c79e9ecf72fce021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25f0205de7104563e82e8f2fd1c8ceb614ecfae421c7bfa28ffa5a75902a57d4 0.600000000000 1638542 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": 1152945, "vin": [ { "gen": { "height": 1152935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25f0205de7104563e82e8f2fd1c8ceb614ecfae421c7bfa28ffa5a75902a57d4" } } ], "extra": [ 1, 38, 221, 202, 214, 140, 86, 27, 139, 155, 204, 233, 49, 76, 203, 51, 52, 130, 118, 50, 139, 252, 83, 49, 114, 230, 156, 121, 233, 236, 247, 47, 206, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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