Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41ee88b0a84ab4f33b303b782e31103c8deabe4b140d91601a2773dabf88631

Tx prefix hash: 104a680c69a5b965ced79e7b66e280267ba1da58f6a2bd84585f3d94a80b0b9e
Tx public key: e0e6878dae66bb98cf12f668c59016c01eb2bf25a93c0d980b80cb38a4c9eefd
Timestamp: 1733554753 Timestamp [UCT]: 2024-12-07 06:59:13 Age [y:d:h:m:s]: 00:140:05:51:35
Block: 1169829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100051 RingCT/type: yes/0
Extra: 01e0e6878dae66bb98cf12f668c59016c01eb2bf25a93c0d980b80cb38a4c9eefd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7a093e2c7a8eae4e251605f6767297bfaf4808ef37235e2c25f42d83d216ab2 0.600000000000 1655554 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": 1169839, "vin": [ { "gen": { "height": 1169829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7a093e2c7a8eae4e251605f6767297bfaf4808ef37235e2c25f42d83d216ab2" } } ], "extra": [ 1, 224, 230, 135, 141, 174, 102, 187, 152, 207, 18, 246, 104, 197, 144, 22, 192, 30, 178, 191, 37, 169, 60, 13, 152, 11, 128, 203, 56, 164, 201, 238, 253, 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