Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6c9f2cc2c22fe3929e053e9105e72922f7317cfb178dcda9a5b76894b41812

Tx prefix hash: 354554de25df3e7d36fa8f350ede3b4c164178577dbe47eedde6a02d2f6bffa8
Tx public key: 3069b55a0c989a8cfa1d437e311f0ace566173f28fd91f38cc612378b1a1438e
Timestamp: 1714059513 Timestamp [UCT]: 2024-04-25 15:38:33 Age [y:d:h:m:s]: 00:346:09:54:10
Block: 1008303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247628 RingCT/type: yes/0
Extra: 013069b55a0c989a8cfa1d437e311f0ace566173f28fd91f38cc612378b1a1438e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf6c171067aa71a0764e933bb75fd0fc6787e5213ce4ce0eb348774c38b61a13 0.600000000000 1469771 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": 1008313, "vin": [ { "gen": { "height": 1008303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf6c171067aa71a0764e933bb75fd0fc6787e5213ce4ce0eb348774c38b61a13" } } ], "extra": [ 1, 48, 105, 181, 90, 12, 152, 154, 140, 250, 29, 67, 126, 49, 31, 10, 206, 86, 97, 115, 242, 143, 217, 31, 56, 204, 97, 35, 120, 177, 161, 67, 142, 2, 17, 0, 0, 0, 1, 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