Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1cfe1396789e45dce0f12d200470e921c7731a04583902d4e5822a7a73a448f

Tx prefix hash: 8db546532d6a828e6c8760a8c71d979bb647a5b2b6f02420eb764e505f339d3c
Tx public key: 44533b87a8220c0288fa2aa5ad220f2c9cf832aaeccee438b5b4eae4337dcd05
Timestamp: 1648620627 Timestamp [UCT]: 2022-03-30 06:10:27 Age [y:d:h:m:s]: 02:358:16:33:43
Block: 469401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775734 RingCT/type: yes/0
Extra: 0144533b87a8220c0288fa2aa5ad220f2c9cf832aaeccee438b5b4eae4337dcd0502110000000837cb3088000000000000000000

1 output(s) for total of 17.087553201000 dcy

stealth address amount amount idx
00: 735edfa71958a338e0567062cf71f099d40464a593ebdf0661f74655f294e063 17.087553201000 888341 of 0

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": 469411, "vin": [ { "gen": { "height": 469401 } } ], "vout": [ { "amount": 17087553201, "target": { "key": "735edfa71958a338e0567062cf71f099d40464a593ebdf0661f74655f294e063" } } ], "extra": [ 1, 68, 83, 59, 135, 168, 34, 12, 2, 136, 250, 42, 165, 173, 34, 15, 44, 156, 248, 50, 170, 236, 206, 228, 56, 181, 180, 234, 228, 51, 125, 205, 5, 2, 17, 0, 0, 0, 8, 55, 203, 48, 136, 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