Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc92916a02186aa6ff6523bd6c31bcb743b29ee84f3ad44c6f4357f8489c5cc1

Tx prefix hash: fa5a174cfbddedab4031ab194c98d7132a624ad4644da1f79392c1df685af22e
Tx public key: 0d62584a0c307adaadbb19dd69d0ab13dd3a5e20e39af8cf5449d077314ab2f3
Timestamp: 1718740677 Timestamp [UCT]: 2024-06-18 19:57:57 Age [y:d:h:m:s]: 00:287:00:24:03
Block: 1047112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205088 RingCT/type: yes/0
Extra: 010d62584a0c307adaadbb19dd69d0ab13dd3a5e20e39af8cf5449d077314ab2f302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c14d31a67b4ebd81b31ef5827e8ea1953a2c10dbffd9b1bc139993adf1c4b4c2 0.600000000000 1516931 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": 1047122, "vin": [ { "gen": { "height": 1047112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c14d31a67b4ebd81b31ef5827e8ea1953a2c10dbffd9b1bc139993adf1c4b4c2" } } ], "extra": [ 1, 13, 98, 88, 74, 12, 48, 122, 218, 173, 187, 25, 221, 105, 208, 171, 19, 221, 58, 94, 32, 227, 154, 248, 207, 84, 73, 208, 119, 49, 74, 178, 243, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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