Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8db02d23b40ae5e2d18c2ba22278c03f45482ed09d4a5ccc2a9e4fbcd1b9f420

Tx prefix hash: d250e939f44fd9f77d4654ce693c854dc8dd83e9bad755816f28aad4af27902a
Tx public key: 46e6b80d4df883c894c8fa8662fd823334c589cf555ed574dec9aad9bccb2491
Timestamp: 1739585410 Timestamp [UCT]: 2025-02-15 02:10:10 Age [y:d:h:m:s]: 00:279:09:51:28
Block: 1219520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197414 RingCT/type: yes/0
Extra: 0146e6b80d4df883c894c8fa8662fd823334c589cf555ed574dec9aad9bccb24910211000000a88377ed96000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 578531b57e0a9c300404c112712e993d0f32e8c98faf2eb0e0af2c11f7ddf5d0 0.600000000000 1706345 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": 1219530, "vin": [ { "gen": { "height": 1219520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "578531b57e0a9c300404c112712e993d0f32e8c98faf2eb0e0af2c11f7ddf5d0" } } ], "extra": [ 1, 70, 230, 184, 13, 77, 248, 131, 200, 148, 200, 250, 134, 98, 253, 130, 51, 52, 197, 137, 207, 85, 94, 213, 116, 222, 201, 170, 217, 188, 203, 36, 145, 2, 17, 0, 0, 0, 168, 131, 119, 237, 150, 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