Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec83d77752897d59355f5ec5e681bf52d0672c2d033fd331fa6b68988fe5a69

Tx prefix hash: bca2d1bc82093a93920151f85884472eac7c1f967a85f9be47cbaa702423b241
Tx public key: 1b3f028dd99a1a38c385c12b92ead7fe110161f2c942bd6a7a19cd4db2182c9b
Timestamp: 1736844859 Timestamp [UCT]: 2025-01-14 08:54:19 Age [y:d:h:m:s]: 00:154:22:32:04
Block: 1197063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110436 RingCT/type: yes/0
Extra: 011b3f028dd99a1a38c385c12b92ead7fe110161f2c942bd6a7a19cd4db2182c9b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d1bbe691d664fceb82b6e028dfdebe91ac4b44e24713cfee52ba1ba66580681 0.600000000000 1683668 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": 1197073, "vin": [ { "gen": { "height": 1197063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d1bbe691d664fceb82b6e028dfdebe91ac4b44e24713cfee52ba1ba66580681" } } ], "extra": [ 1, 27, 63, 2, 141, 217, 154, 26, 56, 195, 133, 193, 43, 146, 234, 215, 254, 17, 1, 97, 242, 201, 66, 189, 106, 122, 25, 205, 77, 178, 24, 44, 155, 2, 17, 0, 0, 0, 1, 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