Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d623899805d80d50aab9a78b1756d0f4873b084503ac0dbdcd046d6e76c65b9d

Tx prefix hash: f1ffb6939127f8239f2f563b7f6370756478fbc502bf01632d6d7a17b2d709e3
Tx public key: 05a63e64c960a1ae47e9b6bc4afad86ca70082e987f9386bbb4b728cde4a426a
Timestamp: 1704858568 Timestamp [UCT]: 2024-01-10 03:49:28 Age [y:d:h:m:s]: 01:158:22:31:40
Block: 932014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374633 RingCT/type: yes/0
Extra: 0105a63e64c960a1ae47e9b6bc4afad86ca70082e987f9386bbb4b728cde4a426a0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9fa2ded37b5bff59e53cf849b4acb5ee949c9535052a8ea3d672d650a96dac0 0.600000000000 1389926 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": 932024, "vin": [ { "gen": { "height": 932014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9fa2ded37b5bff59e53cf849b4acb5ee949c9535052a8ea3d672d650a96dac0" } } ], "extra": [ 1, 5, 166, 62, 100, 201, 96, 161, 174, 71, 233, 182, 188, 74, 250, 216, 108, 167, 0, 130, 233, 135, 249, 56, 107, 187, 75, 114, 140, 222, 74, 66, 106, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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