Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96acca6508a646c8d9211523b5204f8912804dd250725c78381dafefbb7e2917

Tx prefix hash: 6e2d6d5c8f1162176b22e8011dc3ff886c5f7973226e589f8009cca72a1e1a6c
Tx public key: b274105700346e8e69ece1480fdf911fb6ff893c254d18a9b34f9ab00d464dc3
Timestamp: 1737985940 Timestamp [UCT]: 2025-01-27 13:52:20 Age [y:d:h:m:s]: 00:144:18:04:12
Block: 1206261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103350 RingCT/type: yes/0
Extra: 01b274105700346e8e69ece1480fdf911fb6ff893c254d18a9b34f9ab00d464dc3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455ef6654db2390d5536fca940fb4b542b7b60abcb127fd4414b9e9efba9a037 0.600000000000 1692964 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": 1206271, "vin": [ { "gen": { "height": 1206261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455ef6654db2390d5536fca940fb4b542b7b60abcb127fd4414b9e9efba9a037" } } ], "extra": [ 1, 178, 116, 16, 87, 0, 52, 110, 142, 105, 236, 225, 72, 15, 223, 145, 31, 182, 255, 137, 60, 37, 77, 24, 169, 179, 79, 154, 176, 13, 70, 77, 195, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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