Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e72c18bb02f9b14c36862bd3b67f9dc10094755c81923a0df9b470736fac4fe5

Tx prefix hash: 96e8d4432def45eb5189b1fd97ed0ae287029dadd09692b7bfa37c9de47ce8d1
Tx public key: 0a45e96707395909663804258a5aa3c60ad170719f956f29fed7c7a2efedb9d1
Timestamp: 1717277594 Timestamp [UCT]: 2024-06-01 21:33:14 Age [y:d:h:m:s]: 00:296:11:05:09
Block: 1034999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211856 RingCT/type: yes/0
Extra: 010a45e96707395909663804258a5aa3c60ad170719f956f29fed7c7a2efedb9d102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14b017f5f612c41c9fba17e7de42707e47951ca1559a2fb433fefee52b04089f 0.600000000000 1503518 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": 1035009, "vin": [ { "gen": { "height": 1034999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14b017f5f612c41c9fba17e7de42707e47951ca1559a2fb433fefee52b04089f" } } ], "extra": [ 1, 10, 69, 233, 103, 7, 57, 89, 9, 102, 56, 4, 37, 138, 90, 163, 198, 10, 209, 112, 113, 159, 149, 111, 41, 254, 215, 199, 162, 239, 237, 185, 209, 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