Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3735090d2171ec2c0b8dfbb37284c945b1e7cb9c8ab9a7069cc860761cec520

Tx prefix hash: 1ad922a23f647e47380059d83ef19267ad0011ba6c7a56ea1d07d5bbf9afcee9
Tx public key: a7ec11d4e344b006191ad8d2d505b3de1a97c8546f18da0a7b9ebd2898e5f52a
Timestamp: 1734183363 Timestamp [UCT]: 2024-12-14 13:36:03 Age [y:d:h:m:s]: 00:188:05:46:33
Block: 1175050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134191 RingCT/type: yes/0
Extra: 01a7ec11d4e344b006191ad8d2d505b3de1a97c8546f18da0a7b9ebd2898e5f52a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e64dab85c2e30ca6401bcb12c13e94ccc8894b9c412050ae1e936326e90294f 0.600000000000 1661279 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": 1175060, "vin": [ { "gen": { "height": 1175050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e64dab85c2e30ca6401bcb12c13e94ccc8894b9c412050ae1e936326e90294f" } } ], "extra": [ 1, 167, 236, 17, 212, 227, 68, 176, 6, 25, 26, 216, 210, 213, 5, 179, 222, 26, 151, 200, 84, 111, 24, 218, 10, 123, 158, 189, 40, 152, 229, 245, 42, 2, 17, 0, 0, 0, 3, 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