Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6dafcdf7df67b6adcd5700678f3b9ab656b792dc2b741000c4d38058898d0b7

Tx prefix hash: 36be00bc23ce2be6aefe73910ff0fef6b5795e216b218bd5bd7a17632dc4ea7b
Tx public key: 8bdd4634f89f7b124b508b5b2e16bcb4a9e97e1304b24bf1a84bbbf44ea2c4a5
Timestamp: 1726411517 Timestamp [UCT]: 2024-09-15 14:45:17 Age [y:d:h:m:s]: 00:204:15:04:07
Block: 1110714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146059 RingCT/type: yes/0
Extra: 018bdd4634f89f7b124b508b5b2e16bcb4a9e97e1304b24bf1a84bbbf44ea2c4a502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74c2e48863fabb83d5a96a7f821228b50ed6351a673e0f33544e6c8b4b492cd0 0.600000000000 1589415 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": 1110724, "vin": [ { "gen": { "height": 1110714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74c2e48863fabb83d5a96a7f821228b50ed6351a673e0f33544e6c8b4b492cd0" } } ], "extra": [ 1, 139, 221, 70, 52, 248, 159, 123, 18, 75, 80, 139, 91, 46, 22, 188, 180, 169, 233, 126, 19, 4, 178, 75, 241, 168, 75, 187, 244, 78, 162, 196, 165, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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