Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffbc5636c657e73b287dc04e088fd8811d5222ec3cb24cf7a2b0f6b36bed49ae

Tx prefix hash: 3c45d3614c1cd3569221697ed0b8ffb79ce918e4b5bb61d95d5a7b85f884c1fd
Tx public key: ed797d6519de8f989db165996edb71df14c592080a72b7efc2e255b42db870f8
Timestamp: 1710006267 Timestamp [UCT]: 2024-03-09 17:44:27 Age [y:d:h:m:s]: 01:080:08:53:50
Block: 974708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318474 RingCT/type: yes/0
Extra: 01ed797d6519de8f989db165996edb71df14c592080a72b7efc2e255b42db870f80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0ab06b15881f8e9170b4c7b0fb0a1a0a04009920dd35b5611232bb3bd60e5f8 0.600000000000 1434667 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": 974718, "vin": [ { "gen": { "height": 974708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ab06b15881f8e9170b4c7b0fb0a1a0a04009920dd35b5611232bb3bd60e5f8" } } ], "extra": [ 1, 237, 121, 125, 101, 25, 222, 143, 152, 157, 177, 101, 153, 110, 219, 113, 223, 20, 197, 146, 8, 10, 114, 183, 239, 194, 226, 85, 180, 45, 184, 112, 248, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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