Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b28df478a56f6c4a8a75e50d93e6d6d44d363dcb20568cfaa4f0f9d5c471498

Tx prefix hash: a004045a900a4933069e035790780bf7fee7ab063284b24e72d748bec21b0da1
Tx public key: 7796d59af9e88a28a9dea9ab93ca0c10d47b543032a7611d983c0ccb1d673a14
Timestamp: 1707891795 Timestamp [UCT]: 2024-02-14 06:23:15 Age [y:d:h:m:s]: 01:062:07:13:09
Block: 957159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305583 RingCT/type: yes/0
Extra: 017796d59af9e88a28a9dea9ab93ca0c10d47b543032a7611d983c0ccb1d673a1402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d2f56185d5994798d01c835cb1d58126d34fd4bdf88d0fe9ea7f763457b11b9 0.600000000000 1416475 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": 957169, "vin": [ { "gen": { "height": 957159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d2f56185d5994798d01c835cb1d58126d34fd4bdf88d0fe9ea7f763457b11b9" } } ], "extra": [ 1, 119, 150, 213, 154, 249, 232, 138, 40, 169, 222, 169, 171, 147, 202, 12, 16, 212, 123, 84, 48, 50, 167, 97, 29, 152, 60, 12, 203, 29, 103, 58, 20, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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