Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d444b41908ee2d2f00a7bb71e3b33c24720e281e48c8a4c8b5a18abd77fe44

Tx prefix hash: 0d887f0c450cd528fc915b1c577626e93930e7fd3f3e6fe93daa05e1e8843a5c
Tx public key: 0bec2687545058fa914e2980a69df16d067b7e047465ff36976151102c6b1986
Timestamp: 1713400226 Timestamp [UCT]: 2024-04-18 00:30:26 Age [y:d:h:m:s]: 01:061:12:51:04
Block: 1002818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304847 RingCT/type: yes/0
Extra: 010bec2687545058fa914e2980a69df16d067b7e047465ff36976151102c6b19860211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 085d7d6b724a76164273b50f0c5fc6f67527991d53ddd4c356c6f01739bdca56 0.600000000000 1463344 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": 1002828, "vin": [ { "gen": { "height": 1002818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "085d7d6b724a76164273b50f0c5fc6f67527991d53ddd4c356c6f01739bdca56" } } ], "extra": [ 1, 11, 236, 38, 135, 84, 80, 88, 250, 145, 78, 41, 128, 166, 157, 241, 109, 6, 123, 126, 4, 116, 101, 255, 54, 151, 97, 81, 16, 44, 107, 25, 134, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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