Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaca0291b533c7ec3f8fca3de416c37bed0ba2fb4720586c49c295414898c0ef

Tx prefix hash: f253b2ccd96235079b20ddf4a3bba710fcf406904810ce885ab317f6e58400f2
Tx public key: 8ea989b3cde2bdcbada027bdaa8c331b0fa94f5566e191fa3e40bea69ace6320
Timestamp: 1732323067 Timestamp [UCT]: 2024-11-23 00:51:07 Age [y:d:h:m:s]: 00:353:00:23:46
Block: 1159631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249824 RingCT/type: yes/0
Extra: 018ea989b3cde2bdcbada027bdaa8c331b0fa94f5566e191fa3e40bea69ace6320021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d40cccdf32c692cae55334eaaf09b346d6fffb6135bd96f4b5ff1f8c595ee24 0.600000000000 1645270 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": 1159641, "vin": [ { "gen": { "height": 1159631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d40cccdf32c692cae55334eaaf09b346d6fffb6135bd96f4b5ff1f8c595ee24" } } ], "extra": [ 1, 142, 169, 137, 179, 205, 226, 189, 203, 173, 160, 39, 189, 170, 140, 51, 27, 15, 169, 79, 85, 102, 225, 145, 250, 62, 64, 190, 166, 154, 206, 99, 32, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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