Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e74ced1477eb75a4a99ee8b51c349effb5235947a2d2996a553dddb6267458e

Tx prefix hash: cc17463df7e94df9d21acc72db287fbebb844c2426d11a1f8cb56ff57018325f
Tx public key: 8893272378f5aea35d817de4f7449132c2ff4313a9b3c825e5917bca19878dd5
Timestamp: 1702628121 Timestamp [UCT]: 2023-12-15 08:15:21 Age [y:d:h:m:s]: 01:330:18:01:31
Block: 913529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495245 RingCT/type: yes/0
Extra: 018893272378f5aea35d817de4f7449132c2ff4313a9b3c825e5917bca19878dd502110000000b33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91b15f1aad5a6de03791c09c4cd26f908c1410bb69e8b352924f9a0bf8de2af9 0.600000000000 1370801 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": 913539, "vin": [ { "gen": { "height": 913529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91b15f1aad5a6de03791c09c4cd26f908c1410bb69e8b352924f9a0bf8de2af9" } } ], "extra": [ 1, 136, 147, 39, 35, 120, 245, 174, 163, 93, 129, 125, 228, 247, 68, 145, 50, 194, 255, 67, 19, 169, 179, 200, 37, 229, 145, 123, 202, 25, 135, 141, 213, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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