Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 801fc9c6d5eafc9368a164eeea3c002add3fb8418cfc95f02568bdf4e329ae8b

Tx prefix hash: 2d52bef706153d886bef7a57329e7f545ae9a1b2b7ee4c3243ff124f98f0a930
Tx public key: 506cc401a3eccb6d37a256d25703e9fdcf8885c24b94156edd0808bcf3f3492b
Timestamp: 1740791591 Timestamp [UCT]: 2025-03-01 01:13:11 Age [y:d:h:m:s]: 00:012:07:07:34
Block: 1229456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8826 RingCT/type: yes/0
Extra: 01506cc401a3eccb6d37a256d25703e9fdcf8885c24b94156edd0808bcf3f3492b02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c3fb09cb4889d5e9f88ba45fd44ae15c79c495d4b8af8693ff7fff52e2d7aae 0.600000000000 1716343 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": 1229466, "vin": [ { "gen": { "height": 1229456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c3fb09cb4889d5e9f88ba45fd44ae15c79c495d4b8af8693ff7fff52e2d7aae" } } ], "extra": [ 1, 80, 108, 196, 1, 163, 236, 203, 109, 55, 162, 86, 210, 87, 3, 233, 253, 207, 136, 133, 194, 75, 148, 21, 110, 221, 8, 8, 188, 243, 243, 73, 43, 2, 17, 0, 0, 0, 11, 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