Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 141ba01bb3a013414741f3acc7f1d6807b2766a1567c793047a4fba634c908af

Tx prefix hash: 3945c294d617987021cf7bea4c6d4b4bd60ff45d41a55f2c83d714b6277e6dd1
Tx public key: 2523f38b84e74e7ed427b54807be4cde817a8d8e9d5b2a7d0988121cd60bd156
Timestamp: 1720371707 Timestamp [UCT]: 2024-07-07 17:01:47 Age [y:d:h:m:s]: 00:311:23:49:02
Block: 1060636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222946 RingCT/type: yes/0
Extra: 012523f38b84e74e7ed427b54807be4cde817a8d8e9d5b2a7d0988121cd60bd156021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2997765931536ae503888d32ebb41a07200d90dd8dd2e25d883ca8948b1c8bc3 0.600000000000 1531121 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": 1060646, "vin": [ { "gen": { "height": 1060636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2997765931536ae503888d32ebb41a07200d90dd8dd2e25d883ca8948b1c8bc3" } } ], "extra": [ 1, 37, 35, 243, 139, 132, 231, 78, 126, 212, 39, 181, 72, 7, 190, 76, 222, 129, 122, 141, 142, 157, 91, 42, 125, 9, 136, 18, 28, 214, 11, 209, 86, 2, 17, 0, 0, 0, 6, 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