Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e9c00bd7fdb00b672d2b01b823e07d4d7a837b6d2f618fa4ebf0068cb7d586d

Tx prefix hash: 1d11203b28cbd075affb8633fa8375d1604e82859d8a7416eda64a89c62d899c
Tx public key: 4fb2c39aca4a530d7574b4932d56f3eaf965494ae7eca55d3c94fec62ff81639
Timestamp: 1733142091 Timestamp [UCT]: 2024-12-02 12:21:31 Age [y:d:h:m:s]: 00:341:21:14:02
Block: 1166406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241869 RingCT/type: yes/0
Extra: 014fb2c39aca4a530d7574b4932d56f3eaf965494ae7eca55d3c94fec62ff81639021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5626c5624e0d4b7dfecb5056c90eb961a168457ad4a452a11f44970bf0d4bbc 0.600000000000 1652093 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": 1166416, "vin": [ { "gen": { "height": 1166406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5626c5624e0d4b7dfecb5056c90eb961a168457ad4a452a11f44970bf0d4bbc" } } ], "extra": [ 1, 79, 178, 195, 154, 202, 74, 83, 13, 117, 116, 180, 147, 45, 86, 243, 234, 249, 101, 73, 74, 231, 236, 165, 93, 60, 148, 254, 198, 47, 248, 22, 57, 2, 17, 0, 0, 0, 3, 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