Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2334fd7f0cd4c2b0e5bc038cbe7327d42502e05e4af47a31c9d7e20c3a1465

Tx prefix hash: 191614b4d2d8044576817f8468d97337c17b15c7bae48ac93fd7e3ff27a7aa7d
Tx public key: 517b451a76cd07ad9ab980dfa759b574ae9555e8c09bb68cda02d6fbb064bc71
Timestamp: 1697429277 Timestamp [UCT]: 2023-10-16 04:07:57 Age [y:d:h:m:s]: 01:209:17:48:31
Block: 870637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410950 RingCT/type: yes/0
Extra: 01517b451a76cd07ad9ab980dfa759b574ae9555e8c09bb68cda02d6fbb064bc7102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.800236261000 dcy

stealth address amount amount idx
00: f075b540dffecf06f6994a0a9de4ed8f10815eb5b8b50a6363a757b32f2d3f60 0.800236261000 1325520 of 0

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": 870647, "vin": [ { "gen": { "height": 870637 } } ], "vout": [ { "amount": 800236261, "target": { "key": "f075b540dffecf06f6994a0a9de4ed8f10815eb5b8b50a6363a757b32f2d3f60" } } ], "extra": [ 1, 81, 123, 69, 26, 118, 205, 7, 173, 154, 185, 128, 223, 167, 89, 181, 116, 174, 149, 85, 232, 192, 155, 182, 140, 218, 2, 214, 251, 176, 100, 188, 113, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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