Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f124a7ab167dcef43a37e7f0f753355abce444fd0ee24d4486b2c00d32b2d8

Tx prefix hash: a1cc33ed833d634c48bc0143a6fecd1587a9e41c3774ef5709b75c9876a026a0
Tx public key: 481efd01e26cc876c9d1ca83537de67f56236928d981ab6bf1f3aeaede88d313
Timestamp: 1732852183 Timestamp [UCT]: 2024-11-29 03:49:43 Age [y:d:h:m:s]: 00:041:00:18:00
Block: 1164006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29339 RingCT/type: yes/0
Extra: 01481efd01e26cc876c9d1ca83537de67f56236928d981ab6bf1f3aeaede88d3130211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fa3f000a18a15e9e4c8b3f68e1c85053fbcc8508035b9da5cfc4422cb341c5a 0.600000000000 1649677 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": 1164016, "vin": [ { "gen": { "height": 1164006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fa3f000a18a15e9e4c8b3f68e1c85053fbcc8508035b9da5cfc4422cb341c5a" } } ], "extra": [ 1, 72, 30, 253, 1, 226, 108, 200, 118, 201, 209, 202, 131, 83, 125, 230, 127, 86, 35, 105, 40, 217, 129, 171, 107, 241, 243, 174, 174, 222, 136, 211, 19, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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