Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7ef33ed7fcdf438d8743887e72ecde97f7958801b765cbbf98ee4219e7f2b93

Tx prefix hash: 55a013ebeaeaccf68fdd39909c43be764d9da679b5a8ceef1e3991e8905a1143
Tx public key: 9bd35ef3fda54a87c38d24ebccc54542972f8cda4edd67a1a4a90e33bf8f2d1e
Timestamp: 1736893558 Timestamp [UCT]: 2025-01-14 22:25:58 Age [y:d:h:m:s]: 00:341:03:11:07
Block: 1197465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241371 RingCT/type: yes/0
Extra: 019bd35ef3fda54a87c38d24ebccc54542972f8cda4edd67a1a4a90e33bf8f2d1e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1423f5df8cf9d98fa98dcc66702ebe0df69de52f1b8693faf5fd496ce1d138c 0.600000000000 1684072 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": 1197475, "vin": [ { "gen": { "height": 1197465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1423f5df8cf9d98fa98dcc66702ebe0df69de52f1b8693faf5fd496ce1d138c" } } ], "extra": [ 1, 155, 211, 94, 243, 253, 165, 74, 135, 195, 141, 36, 235, 204, 197, 69, 66, 151, 47, 140, 218, 78, 221, 103, 161, 164, 169, 14, 51, 191, 143, 45, 30, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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