Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 629acd63b204c765c0b6a497b1f2d880d4ac1702f49524996580f061168e49f6

Tx prefix hash: 4c3f22d2e10c0170e8c42e39a52afe89897b50bd66f58ebadd632ed82b324466
Tx public key: a0fa16a772bc7ae2c4bf9a82033a7120784b925800856d38adb0acf0beaa8998
Timestamp: 1631524100 Timestamp [UCT]: 2021-09-13 09:08:20 Age [y:d:h:m:s]: 03:243:00:55:39
Block: 332848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 949102 RingCT/type: yes/0
Extra: 01a0fa16a772bc7ae2c4bf9a82033a7120784b925800856d38adb0acf0beaa899802110000001cf29d7abf000000000000000000

1 output(s) for total of 48.435015478000 dcy

stealth address amount amount idx
00: 7f3a380feffc4f901a27874bf77038a27b6a5f82c2728e071148abe8d4598179 48.435015478000 687133 of 0

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": 332858, "vin": [ { "gen": { "height": 332848 } } ], "vout": [ { "amount": 48435015478, "target": { "key": "7f3a380feffc4f901a27874bf77038a27b6a5f82c2728e071148abe8d4598179" } } ], "extra": [ 1, 160, 250, 22, 167, 114, 188, 122, 226, 196, 191, 154, 130, 3, 58, 113, 32, 120, 75, 146, 88, 0, 133, 109, 56, 173, 176, 172, 240, 190, 170, 137, 152, 2, 17, 0, 0, 0, 28, 242, 157, 122, 191, 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