Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e14beda9430bac3640b9c0be29091f1f6ca661614c7c5d36679d8b796c8e3f3

Tx prefix hash: adcf5ce13feb6082d1ddd4053d1ed3184105f3e200124a056088f642d4c5d297
Tx public key: 8bcc6f3b6f77aadd1db5bed6569907389d8fa5ea4828672362f1dd35a7a7dac5
Timestamp: 1709214591 Timestamp [UCT]: 2024-02-29 13:49:51 Age [y:d:h:m:s]: 01:251:10:14:11
Block: 968145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438410 RingCT/type: yes/0
Extra: 018bcc6f3b6f77aadd1db5bed6569907389d8fa5ea4828672362f1dd35a7a7dac502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ee347838f915df2a6d0752ab56211e17d9d641589800624a80c60c7a892c565 0.600000000000 1427944 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": 968155, "vin": [ { "gen": { "height": 968145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ee347838f915df2a6d0752ab56211e17d9d641589800624a80c60c7a892c565" } } ], "extra": [ 1, 139, 204, 111, 59, 111, 119, 170, 221, 29, 181, 190, 214, 86, 153, 7, 56, 157, 143, 165, 234, 72, 40, 103, 35, 98, 241, 221, 53, 167, 167, 218, 197, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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