Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3277f61108d48541c4fd0315883ba75b92648f2f2dd5cfedc83c2715f744be2e

Tx prefix hash: b9f2813607276e0489ce6f1087b0f3552825a53f2ab6266691cde379493aba83
Tx public key: 0b7caf3494e1806a62906dd28b9ca6215c125f7d1f5e7a22a2e72100fa6f3c89
Timestamp: 1734786172 Timestamp [UCT]: 2024-12-21 13:02:52 Age [y:d:h:m:s]: 00:024:02:10:16
Block: 1180050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17200 RingCT/type: yes/0
Extra: 010b7caf3494e1806a62906dd28b9ca6215c125f7d1f5e7a22a2e72100fa6f3c89021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f86c684179c2aa38edc603b9c4d4c928009f54ac0b41a196619a5a72953f83a 0.600000000000 1666455 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": 1180060, "vin": [ { "gen": { "height": 1180050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f86c684179c2aa38edc603b9c4d4c928009f54ac0b41a196619a5a72953f83a" } } ], "extra": [ 1, 11, 124, 175, 52, 148, 225, 128, 106, 98, 144, 109, 210, 139, 156, 166, 33, 92, 18, 95, 125, 31, 94, 122, 34, 162, 231, 33, 0, 250, 111, 60, 137, 2, 17, 0, 0, 0, 2, 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