Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05dee44ef26544007a462d15cd61241e67944dd6066b23edb76afc46980a7862

Tx prefix hash: 9f7e11bb20175a15320e742bb12c6d6c311f02d5385ff17d18db46c713b7f2c1
Tx public key: b4e4494bee257475da6f26fe7d2b90078a04f1927dbe277bba286aa5cb0a034c
Timestamp: 1725180844 Timestamp [UCT]: 2024-09-01 08:54:04 Age [y:d:h:m:s]: 00:229:09:12:31
Block: 1100510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163799 RingCT/type: yes/0
Extra: 01b4e4494bee257475da6f26fe7d2b90078a04f1927dbe277bba286aa5cb0a034c02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6ec7ce9c5a7beb318cb9473a32ba8586c359fce032862a79e47c220d281c9c8 0.600000000000 1576489 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": 1100520, "vin": [ { "gen": { "height": 1100510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6ec7ce9c5a7beb318cb9473a32ba8586c359fce032862a79e47c220d281c9c8" } } ], "extra": [ 1, 180, 228, 73, 75, 238, 37, 116, 117, 218, 111, 38, 254, 125, 43, 144, 7, 138, 4, 241, 146, 125, 190, 39, 123, 186, 40, 106, 165, 203, 10, 3, 76, 2, 17, 0, 0, 0, 11, 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