Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e1d5d3f0ad2909b5bd534b1f5932cb3080af1fb27738ff53e1ef1c3dbe3b41

Tx prefix hash: dfe43a4f8b0b5df45d7570545e70feab60652b2ee6cf3b329722d2cb90a6c9dd
Tx public key: 6b3156df7fa154a42ddc9e771bd909529054a4fbd7219118c49ed7c036df5e9a
Timestamp: 1734069954 Timestamp [UCT]: 2024-12-13 06:05:54 Age [y:d:h:m:s]: 00:328:19:22:26
Block: 1174113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232480 RingCT/type: yes/0
Extra: 016b3156df7fa154a42ddc9e771bd909529054a4fbd7219118c49ed7c036df5e9a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1c1eaf25c036d2f1d706a7469e93723d401cfa9d172f065756e0d7b60206a84 0.600000000000 1660222 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": 1174123, "vin": [ { "gen": { "height": 1174113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1c1eaf25c036d2f1d706a7469e93723d401cfa9d172f065756e0d7b60206a84" } } ], "extra": [ 1, 107, 49, 86, 223, 127, 161, 84, 164, 45, 220, 158, 119, 27, 217, 9, 82, 144, 84, 164, 251, 215, 33, 145, 24, 196, 158, 215, 192, 54, 223, 94, 154, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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