Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 370cb7e718f24b19f8ada8370b6d8ad1245a288a8798a79073225c19b67c5a1c

Tx prefix hash: ec625493a9d792942a16961e4ed62340357b59413323996c06b00ec9a5f00a7f
Tx public key: c7f685a7da9ed4cc1b08bf787f185173d2e0f32c9b93fbd9d6915f3460b9d522
Timestamp: 1757982834 Timestamp [UCT]: 2025-09-16 00:33:54 Age [y:d:h:m:s]: 00:138:10:39:03
Block: 1369339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98948 RingCT/type: yes/0
Extra: 01c7f685a7da9ed4cc1b08bf787f185173d2e0f32c9b93fbd9d6915f3460b9d522021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c974dc86e282493263885aff6e25b0b7886d11a2d1112737ef58eec063dc2fa 0.600000000000 1857414 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": 1369349, "vin": [ { "gen": { "height": 1369339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c974dc86e282493263885aff6e25b0b7886d11a2d1112737ef58eec063dc2fa" } } ], "extra": [ 1, 199, 246, 133, 167, 218, 158, 212, 204, 27, 8, 191, 120, 127, 24, 81, 115, 210, 224, 243, 44, 155, 147, 251, 217, 214, 145, 95, 52, 96, 185, 213, 34, 2, 17, 0, 0, 0, 7, 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