Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cac56414da2156003a1c6711e63c956c32ffc54e41ee4de98aad4c3f8c4f704c

Tx prefix hash: 513e83ffa553bb9e634ee5a6d7bbab460345a8abdec542a992ac423f996f8878
Tx public key: 80f6d22a5e9fdf6832f357cae87f0189d473c40914106c35c2c20a03809901f0
Timestamp: 1707788439 Timestamp [UCT]: 2024-02-13 01:40:39 Age [y:d:h:m:s]: 01:268:13:56:05
Block: 956308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450717 RingCT/type: yes/0
Extra: 0180f6d22a5e9fdf6832f357cae87f0189d473c40914106c35c2c20a03809901f00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0edfbd1dc23b5e5ab428ce8dc915f87ecab57165fb380d19df7d0460b86c65a 0.600000000000 1415612 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": 956318, "vin": [ { "gen": { "height": 956308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0edfbd1dc23b5e5ab428ce8dc915f87ecab57165fb380d19df7d0460b86c65a" } } ], "extra": [ 1, 128, 246, 210, 42, 94, 159, 223, 104, 50, 243, 87, 202, 232, 127, 1, 137, 212, 115, 196, 9, 20, 16, 108, 53, 194, 194, 10, 3, 128, 153, 1, 240, 2, 17, 0, 0, 0, 3, 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