Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11958328f453ce4a1b912196d37ff736e9ddb1d4f7098f96de2aaab67715dead

Tx prefix hash: 1389ed68a37d140b1d4dc55f23d8afe7fb1cb4b6fc15270591747a88667d0cf8
Tx public key: 772d7f45868db9297c80fbc9999dbaa4a0f5816c9ffdab9d888f3999839efa56
Timestamp: 1682527706 Timestamp [UCT]: 2023-04-26 16:48:26 Age [y:d:h:m:s]: 01:349:03:39:02
Block: 747139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510791 RingCT/type: yes/0
Extra: 01772d7f45868db9297c80fbc9999dbaa4a0f5816c9ffdab9d888f3999839efa56021100000001faf35c9c000000000000000000

1 output(s) for total of 2.053139924000 dcy

stealth address amount amount idx
00: d0c2b377d0fc5d7e098f377f935cbbf1ad7e8e70f013cca76f7bd12f3eeda1df 2.053139924000 1194780 of 0

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": 747149, "vin": [ { "gen": { "height": 747139 } } ], "vout": [ { "amount": 2053139924, "target": { "key": "d0c2b377d0fc5d7e098f377f935cbbf1ad7e8e70f013cca76f7bd12f3eeda1df" } } ], "extra": [ 1, 119, 45, 127, 69, 134, 141, 185, 41, 124, 128, 251, 201, 153, 157, 186, 164, 160, 245, 129, 108, 159, 253, 171, 157, 136, 143, 57, 153, 131, 158, 250, 86, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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