Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1433de6d33b5b452f46da1911384df7dc34b371c07ce3f46a01f253a01a14eee

Tx prefix hash: 8d5e8943e9ecfc7e742d7113fc3040ab30df7fd1da2e08533ac3d466db8e8db8
Tx public key: 36e14d6840cd98f121e0053b0027b615bbea8be53356f4a072a228298d231af3
Timestamp: 1715718116 Timestamp [UCT]: 2024-05-14 20:21:56 Age [y:d:h:m:s]: 01:033:14:53:03
Block: 1022054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284865 RingCT/type: yes/0
Extra: 0136e14d6840cd98f121e0053b0027b615bbea8be53356f4a072a228298d231af302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 933f95f4173c59360aff35e0d8c94f2cdd4f3fadc85e6d9fd04dcea93312966d 0.600000000000 1486547 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": 1022064, "vin": [ { "gen": { "height": 1022054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "933f95f4173c59360aff35e0d8c94f2cdd4f3fadc85e6d9fd04dcea93312966d" } } ], "extra": [ 1, 54, 225, 77, 104, 64, 205, 152, 241, 33, 224, 5, 59, 0, 39, 182, 21, 187, 234, 139, 229, 51, 86, 244, 160, 114, 162, 40, 41, 141, 35, 26, 243, 2, 17, 0, 0, 0, 1, 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