Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 051ed609f835e0d25b9afe95dce254a6bf2dd7002053d62987accf025413d975

Tx prefix hash: 049bf3a7fc94671c186acd3b975a56ae5331eef75d88a807138550b1ca84bcb8
Tx public key: 697d32a6040c2fd2a2a61e58aae67d2b2ea42d7233bd965162ddb8c1fe8efaed
Timestamp: 1745273657 Timestamp [UCT]: 2025-04-21 22:14:17 Age [y:d:h:m:s]: 00:023:08:49:10
Block: 1266573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16721 RingCT/type: yes/0
Extra: 01697d32a6040c2fd2a2a61e58aae67d2b2ea42d7233bd965162ddb8c1fe8efaed02110000001ddbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7ca8c2cb42f28c99cf61ea9b17a799f0c0a249f9ae837fb650186f470b71e3a 0.600000000000 1753794 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": 1266583, "vin": [ { "gen": { "height": 1266573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7ca8c2cb42f28c99cf61ea9b17a799f0c0a249f9ae837fb650186f470b71e3a" } } ], "extra": [ 1, 105, 125, 50, 166, 4, 12, 47, 210, 162, 166, 30, 88, 170, 230, 125, 43, 46, 164, 45, 114, 51, 189, 150, 81, 98, 221, 184, 193, 254, 142, 250, 237, 2, 17, 0, 0, 0, 29, 219, 181, 113, 193, 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