Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb24f6e68e866a1341b309b35786c09c9b45d73484c4ad013987a509d64e7e0

Tx prefix hash: 1e2ff5fbe018b18588ec0a4e32429c7028e83fd2dfaabd633cb5ea7c4afb22de
Tx public key: 445018ffaa2a40a54b320af398c9a0fa5e7035f842f26c8b308ba481b11ec902
Timestamp: 1734870813 Timestamp [UCT]: 2024-12-22 12:33:33 Age [y:d:h:m:s]: 00:093:23:59:07
Block: 1180750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66928 RingCT/type: yes/0
Extra: 01445018ffaa2a40a54b320af398c9a0fa5e7035f842f26c8b308ba481b11ec902021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39a3f2012e7797b14dbc96789e8def04fb4f99a77f83eb4aed7a8d5557e53ef5 0.600000000000 1667163 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": 1180760, "vin": [ { "gen": { "height": 1180750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39a3f2012e7797b14dbc96789e8def04fb4f99a77f83eb4aed7a8d5557e53ef5" } } ], "extra": [ 1, 68, 80, 24, 255, 170, 42, 64, 165, 75, 50, 10, 243, 152, 201, 160, 250, 94, 112, 53, 248, 66, 242, 108, 139, 48, 139, 164, 129, 177, 30, 201, 2, 2, 17, 0, 0, 0, 2, 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