Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0fbc291c48a8766e06cfc213d48bec878ef31969f04f7bd8c10d3071c586c7e

Tx prefix hash: 6a03b3639e6d2a217725f7a99db967b526bd75974f2b4183dba0ac2679919b04
Tx public key: 1c432cfbabc50ecc7505d9109d44dcba322136ae520aaf0608ba703a41590c7b
Timestamp: 1728814938 Timestamp [UCT]: 2024-10-13 10:22:18 Age [y:d:h:m:s]: 01:026:11:07:27
Block: 1130641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277275 RingCT/type: yes/0
Extra: 011c432cfbabc50ecc7505d9109d44dcba322136ae520aaf0608ba703a41590c7b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6917f0d0140e3329f7b8b83dd8d1997ac8caa9a5438d4c56ec3aa20264c6e0d 0.600000000000 1613518 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": 1130651, "vin": [ { "gen": { "height": 1130641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6917f0d0140e3329f7b8b83dd8d1997ac8caa9a5438d4c56ec3aa20264c6e0d" } } ], "extra": [ 1, 28, 67, 44, 251, 171, 197, 14, 204, 117, 5, 217, 16, 157, 68, 220, 186, 50, 33, 54, 174, 82, 10, 175, 6, 8, 186, 112, 58, 65, 89, 12, 123, 2, 17, 0, 0, 0, 6, 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