Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc7f4bc10cc0cc04e099c8fea92d16b9795074fdf5d2f144a52e4410e1c33d0

Tx prefix hash: 6136d1e5531867348eab60fd6f582d685cb98700df47c3c1ef4046d2eacc1758
Tx public key: 7ad355261d55b2e2d1f7fb2720f83d33ed32d7af70fd32d8c9a2f56f3b66a18d
Timestamp: 1723176528 Timestamp [UCT]: 2024-08-09 04:08:48 Age [y:d:h:m:s]: 01:116:14:22:05
Block: 1083886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341854 RingCT/type: yes/0
Extra: 017ad355261d55b2e2d1f7fb2720f83d33ed32d7af70fd32d8c9a2f56f3b66a18d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd3f6bc245d8741fc04255a5a18b39d5923bba413f84ead7ffe7c515c5321479 0.600000000000 1557965 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": 1083896, "vin": [ { "gen": { "height": 1083886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd3f6bc245d8741fc04255a5a18b39d5923bba413f84ead7ffe7c515c5321479" } } ], "extra": [ 1, 122, 211, 85, 38, 29, 85, 178, 226, 209, 247, 251, 39, 32, 248, 61, 51, 237, 50, 215, 175, 112, 253, 50, 216, 201, 162, 245, 111, 59, 102, 161, 141, 2, 17, 0, 0, 0, 3, 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