Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e90f00ca33a9d8fed1459c93cd9a1b0bf9f75459479381667e0c7d007261004

Tx prefix hash: beaac322eac6807b470bd90c8aee2e62334b2fbdacaf566e54b15d71a1f58f50
Tx public key: 28f7c08f2865252704c42b4c9bf8dae788246c04ba0c2a9116029f08e42c5be3
Timestamp: 1735559263 Timestamp [UCT]: 2024-12-30 11:47:43 Age [y:d:h:m:s]: 00:074:14:15:06
Block: 1186415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53118 RingCT/type: yes/0
Extra: 0128f7c08f2865252704c42b4c9bf8dae788246c04ba0c2a9116029f08e42c5be30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07a23358b0476ea3057bcd9a9d411d27455f13381cb5b085536f2b67602600b7 0.600000000000 1672896 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": 1186425, "vin": [ { "gen": { "height": 1186415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07a23358b0476ea3057bcd9a9d411d27455f13381cb5b085536f2b67602600b7" } } ], "extra": [ 1, 40, 247, 192, 143, 40, 101, 37, 39, 4, 196, 43, 76, 155, 248, 218, 231, 136, 36, 108, 4, 186, 12, 42, 145, 22, 2, 159, 8, 228, 44, 91, 227, 2, 17, 0, 0, 0, 7, 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