Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9131e5ae21c02089424a7aaa12aee3b888306878ddbf5efcdf75b23b7ec7292e

Tx prefix hash: af17b7bd96dbd14bc9bd35e51c7ce4aef6adb48a95914f9e3df2b7bdbd2fa7ff
Tx public key: ec106f7718e4e839b511b839f3f1ed93684f5d5c86ec874110e41555825b5658
Timestamp: 1702245338 Timestamp [UCT]: 2023-12-10 21:55:38 Age [y:d:h:m:s]: 01:047:09:44:16
Block: 910359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295206 RingCT/type: yes/0
Extra: 01ec106f7718e4e839b511b839f3f1ed93684f5d5c86ec874110e41555825b5658021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15a1ba81906565000833457fbaa467636a8d5597847e8bf4f2883e4247dce30f 0.600000000000 1367510 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": 910369, "vin": [ { "gen": { "height": 910359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15a1ba81906565000833457fbaa467636a8d5597847e8bf4f2883e4247dce30f" } } ], "extra": [ 1, 236, 16, 111, 119, 24, 228, 232, 57, 181, 17, 184, 57, 243, 241, 237, 147, 104, 79, 93, 92, 134, 236, 135, 65, 16, 228, 21, 85, 130, 91, 86, 88, 2, 17, 0, 0, 0, 6, 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