Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073423f447d7cf9cd833018ec7526a30c3169ccea258cd654d7d52a9ab11c371

Tx prefix hash: bfc91d404d5952339b788bfe282797c71e629acd62ba1400bfef6fd9eb4a7452
Tx public key: 7450fd0866d9e2cd4a3b636619a2f34b30cb6a7856491f0f43140e70080401af
Timestamp: 1745692725 Timestamp [UCT]: 2025-04-26 18:38:45 Age [y:d:h:m:s]: 00:012:08:47:59
Block: 1270059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8827 RingCT/type: yes/0
Extra: 017450fd0866d9e2cd4a3b636619a2f34b30cb6a7856491f0f43140e70080401af0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d74648d89bea4ae7151582a9481e5a0d5ef2878436b6f9ae5b9ca8cecc78f58 0.600000000000 1757300 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": 1270069, "vin": [ { "gen": { "height": 1270059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d74648d89bea4ae7151582a9481e5a0d5ef2878436b6f9ae5b9ca8cecc78f58" } } ], "extra": [ 1, 116, 80, 253, 8, 102, 217, 226, 205, 74, 59, 99, 102, 25, 162, 243, 75, 48, 203, 106, 120, 86, 73, 31, 15, 67, 20, 14, 112, 8, 4, 1, 175, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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