Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90bcba99645a5120524d130220bc3be7518b4da613eaa5e8d3a2ca2fb0d36067

Tx prefix hash: 09142a6c818f6ab2bcb6bf25ef989612a2a78a13e6afa3e513f4b68ed7e15df7
Tx public key: 4765c91a36092604abdcff648740de58bc78768b599a6903d6c0c5c53bea01b2
Timestamp: 1702030503 Timestamp [UCT]: 2023-12-08 10:15:03 Age [y:d:h:m:s]: 01:131:21:30:27
Block: 908571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355429 RingCT/type: yes/0
Extra: 014765c91a36092604abdcff648740de58bc78768b599a6903d6c0c5c53bea01b202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af2dfbddfd22a3d1a607a073b9b5ea6d1368af93b9364bd9f87231390cfc4bb 0.600000000000 1365610 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": 908581, "vin": [ { "gen": { "height": 908571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af2dfbddfd22a3d1a607a073b9b5ea6d1368af93b9364bd9f87231390cfc4bb" } } ], "extra": [ 1, 71, 101, 201, 26, 54, 9, 38, 4, 171, 220, 255, 100, 135, 64, 222, 88, 188, 120, 118, 139, 89, 154, 105, 3, 214, 192, 197, 197, 59, 234, 1, 178, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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