Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e140094f4cbee9af9b18c3c9684f1cb406af212442f774114e08b86aebdc23b

Tx prefix hash: 4d86c7fd959b1daa90ac35980c554569c960f6e2a47f164e1a45b2c954d377e1
Tx public key: 6a861da96d2f639e48b8395ecd62678d57e57176e180e202e814384590d79b0a
Timestamp: 1732363638 Timestamp [UCT]: 2024-11-23 12:07:18 Age [y:d:h:m:s]: 00:126:18:30:29
Block: 1159961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90407 RingCT/type: yes/0
Extra: 016a861da96d2f639e48b8395ecd62678d57e57176e180e202e814384590d79b0a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13f10e1158e26b91be67931cf7bfeea3aef8b5fa3c07e39da136042fa29a918a 0.600000000000 1645602 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": 1159971, "vin": [ { "gen": { "height": 1159961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13f10e1158e26b91be67931cf7bfeea3aef8b5fa3c07e39da136042fa29a918a" } } ], "extra": [ 1, 106, 134, 29, 169, 109, 47, 99, 158, 72, 184, 57, 94, 205, 98, 103, 141, 87, 229, 113, 118, 225, 128, 226, 2, 232, 20, 56, 69, 144, 215, 155, 10, 2, 17, 0, 0, 0, 1, 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