Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec6654d6700491eb89a6e392b6fdde44e26353e8d2e4d758e5da0e9154d32627

Tx prefix hash: b482e3e65aa31252ef5ec03bcfd91bb48882a051dad6d423306a8582eae865b6
Tx public key: b1dfb57eea817cd30226f286382d1530ce88f038db5e2e6ef673a2f036838243
Timestamp: 1720733533 Timestamp [UCT]: 2024-07-11 21:32:13 Age [y:d:h:m:s]: 01:131:10:29:16
Block: 1063646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352461 RingCT/type: yes/0
Extra: 01b1dfb57eea817cd30226f286382d1530ce88f038db5e2e6ef673a2f036838243021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e56532467d11b737aed4fc01e3312fd9c3fec4b32c346b5083e683676b2663a 0.600000000000 1534163 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": 1063656, "vin": [ { "gen": { "height": 1063646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e56532467d11b737aed4fc01e3312fd9c3fec4b32c346b5083e683676b2663a" } } ], "extra": [ 1, 177, 223, 181, 126, 234, 129, 124, 211, 2, 38, 242, 134, 56, 45, 21, 48, 206, 136, 240, 56, 219, 94, 46, 110, 246, 115, 162, 240, 54, 131, 130, 67, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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