Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793d9c919737acea3f639ab7abe18e91c4ea580fc05c4e0df06145a7bd8998f1

Tx prefix hash: b1bf55ed34d1fa4fea7b7b58e710ee9bd7ff800694f30101cc82878dc2f4c000
Tx public key: c8b4d60e8f23b9bef6e67839f2efb3a80cc9a99a451de8ee026dbef52847037b
Timestamp: 1713693725 Timestamp [UCT]: 2024-04-21 10:02:05 Age [y:d:h:m:s]: 00:216:19:54:49
Block: 1005274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155216 RingCT/type: yes/0
Extra: 01c8b4d60e8f23b9bef6e67839f2efb3a80cc9a99a451de8ee026dbef52847037b0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77c4138e6e0892f9fe588a8e2f14286c0daecc7a7c46c04bc406bd399971aea 0.600000000000 1465860 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": 1005284, "vin": [ { "gen": { "height": 1005274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77c4138e6e0892f9fe588a8e2f14286c0daecc7a7c46c04bc406bd399971aea" } } ], "extra": [ 1, 200, 180, 214, 14, 143, 35, 185, 190, 246, 230, 120, 57, 242, 239, 179, 168, 12, 201, 169, 154, 69, 29, 232, 238, 2, 109, 190, 245, 40, 71, 3, 123, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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