Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1000f951919db8b3c1a8a9a37fb14bffb31feff482ab83c3008afce8ef8b3db4

Tx prefix hash: 7cecbd3d398372cf0fabb02efcd586756dc93305bb00a08e9dea5f2bee5c2b87
Tx public key: 6e99a2275a1b78e2b81c128283af32ce84b69d8a735d90ff3e85d62f1d8676bf
Timestamp: 1741195824 Timestamp [UCT]: 2025-03-05 17:30:24 Age [y:d:h:m:s]: 00:330:15:34:01
Block: 1232821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233983 RingCT/type: yes/0
Extra: 016e99a2275a1b78e2b81c128283af32ce84b69d8a735d90ff3e85d62f1d8676bf0211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc5319bce60ced537ba676d7c0fb8c83bb0b765f1faf1251e4fc0aa6a61082f 0.600000000000 1719736 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": 1232831, "vin": [ { "gen": { "height": 1232821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc5319bce60ced537ba676d7c0fb8c83bb0b765f1faf1251e4fc0aa6a61082f" } } ], "extra": [ 1, 110, 153, 162, 39, 90, 27, 120, 226, 184, 28, 18, 130, 131, 175, 50, 206, 132, 182, 157, 138, 115, 93, 144, 255, 62, 133, 214, 47, 29, 134, 118, 191, 2, 17, 0, 0, 0, 21, 31, 10, 83, 235, 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