Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fedfdf900051ca92a119bfaca15413c96f95f7be8261692c4b8dea6b63081bd7

Tx prefix hash: f7025f7e5ef7c61df14852cbdec4b440a17d8735ae444b991b68994908396b89
Tx public key: d9814ba8f50d3de48d7af83a51db0ebf8ffe20d873ab66b4a03aa8ce4449e85b
Timestamp: 1719054136 Timestamp [UCT]: 2024-06-22 11:02:16 Age [y:d:h:m:s]: 00:246:03:00:45
Block: 1049704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175835 RingCT/type: yes/0
Extra: 01d9814ba8f50d3de48d7af83a51db0ebf8ffe20d873ab66b4a03aa8ce4449e85b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13001d5c0e2020ba7e4c6fb05a4cbe0a1f520dc02e69abc403328781a90221e4 0.600000000000 1519807 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": 1049714, "vin": [ { "gen": { "height": 1049704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13001d5c0e2020ba7e4c6fb05a4cbe0a1f520dc02e69abc403328781a90221e4" } } ], "extra": [ 1, 217, 129, 75, 168, 245, 13, 61, 228, 141, 122, 248, 58, 81, 219, 14, 191, 143, 254, 32, 216, 115, 171, 102, 180, 160, 58, 168, 206, 68, 73, 232, 91, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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