Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2037601419fb94ded1d36f2d22659cd66199a08a2b87f1f1638114215d020ffc

Tx prefix hash: 73acbed2545f367ab9c3773511fb90e40969aada18efb6e1c04b809ae569a9d1
Tx public key: e910e03e5ecf4b8ac2ef209efc0c6cdb2c53b09c8092e58ad61bd491da014eaf
Timestamp: 1733230671 Timestamp [UCT]: 2024-12-03 12:57:51 Age [y:d:h:m:s]: 00:121:13:06:43
Block: 1167144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86661 RingCT/type: yes/0
Extra: 01e910e03e5ecf4b8ac2ef209efc0c6cdb2c53b09c8092e58ad61bd491da014eaf021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b821f3048b7f4e347c08a798e489062a892536b547b56ec935a9170f657f9a9 0.600000000000 1652837 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": 1167154, "vin": [ { "gen": { "height": 1167144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b821f3048b7f4e347c08a798e489062a892536b547b56ec935a9170f657f9a9" } } ], "extra": [ 1, 233, 16, 224, 62, 94, 207, 75, 138, 194, 239, 32, 158, 252, 12, 108, 219, 44, 83, 176, 156, 128, 146, 229, 138, 214, 27, 212, 145, 218, 1, 78, 175, 2, 17, 0, 0, 0, 3, 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