Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55dd96e25eef4bd43a7428784e98ea93035340ea31054445fb86cdbb775a255f

Tx prefix hash: 13edf5c6072b23cfbb099d4ee597347cacaa6a9e2c86d8650795efaec2b2d410
Tx public key: 6cacd85c8827c6d2df71ab19d737e2119f50a9735c75c9563683c5ebb20d914b
Timestamp: 1728932006 Timestamp [UCT]: 2024-10-14 18:53:26 Age [y:d:h:m:s]: 00:101:13:48:13
Block: 1131607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72559 RingCT/type: yes/0
Extra: 016cacd85c8827c6d2df71ab19d737e2119f50a9735c75c9563683c5ebb20d914b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fffc1e9e2e932d5b9ddddb2c8ca7c6bef5d7c7f6f66639db2da74ecfe9b720e 0.600000000000 1614510 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": 1131617, "vin": [ { "gen": { "height": 1131607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fffc1e9e2e932d5b9ddddb2c8ca7c6bef5d7c7f6f66639db2da74ecfe9b720e" } } ], "extra": [ 1, 108, 172, 216, 92, 136, 39, 198, 210, 223, 113, 171, 25, 215, 55, 226, 17, 159, 80, 169, 115, 92, 117, 201, 86, 54, 131, 197, 235, 178, 13, 145, 75, 2, 17, 0, 0, 0, 4, 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