Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74e564e97047e5e103315cbec807d67ed12f53baa823458e9930ea98132bd345

Tx prefix hash: 56423e9a1bd69ac58769a1ef3dd0d33e3bfc867a4ed98d7c61ee1d7e5ea74147
Tx public key: 6d13e3ae31e4e3f88f3e93baec7ad44c81ae31eee38791e141dc4e3ce7a7f274
Timestamp: 1718963420 Timestamp [UCT]: 2024-06-21 09:50:20 Age [y:d:h:m:s]: 00:139:01:30:38
Block: 1048939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99544 RingCT/type: yes/0
Extra: 016d13e3ae31e4e3f88f3e93baec7ad44c81ae31eee38791e141dc4e3ce7a7f27402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f801a22fbbb09f10bf365d6e9d0f4b3186274a2a9c832b2380366b674991601b 0.600000000000 1519030 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": 1048949, "vin": [ { "gen": { "height": 1048939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f801a22fbbb09f10bf365d6e9d0f4b3186274a2a9c832b2380366b674991601b" } } ], "extra": [ 1, 109, 19, 227, 174, 49, 228, 227, 248, 143, 62, 147, 186, 236, 122, 212, 76, 129, 174, 49, 238, 227, 135, 145, 225, 65, 220, 78, 60, 231, 167, 242, 116, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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