Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebfe71f89abcbe9883ea491bd6b9738cb3736429774e8d3b612ff46131281cc9

Tx prefix hash: 67dfc09fa20c3a68e694a3219423eb2a520412e2a18b23942aa0ec7e1198c486
Tx public key: e984313b2b8e7c9f97387121de68990f159b85cdfff6395d41d5143e10dac669
Timestamp: 1710134293 Timestamp [UCT]: 2024-03-11 05:18:13 Age [y:d:h:m:s]: 00:296:08:48:12
Block: 975774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212150 RingCT/type: yes/0
Extra: 01e984313b2b8e7c9f97387121de68990f159b85cdfff6395d41d5143e10dac66902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14a5f65741cd6a40537c8c631e2c77c0f0cc25d9fb8cc18a28541c6e1e34a6b9 0.600000000000 1435749 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": 975784, "vin": [ { "gen": { "height": 975774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a5f65741cd6a40537c8c631e2c77c0f0cc25d9fb8cc18a28541c6e1e34a6b9" } } ], "extra": [ 1, 233, 132, 49, 59, 43, 142, 124, 159, 151, 56, 113, 33, 222, 104, 153, 15, 21, 155, 133, 205, 255, 246, 57, 93, 65, 213, 20, 62, 16, 218, 198, 105, 2, 17, 0, 0, 0, 2, 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