Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539927b7fc3d38e775bcc09d54350bc56d3d99a3eee61944f6c78461001794b7

Tx prefix hash: 14914ce7ade2186c5a6deceed8d3dabea3258ccc3279fbc4409f3ad4eac7b285
Tx public key: 5256e89e45debb4787725a82b42164a4c725d6f11d1fd2c83c1f413e098e47a1
Timestamp: 1712189795 Timestamp [UCT]: 2024-04-04 00:16:35 Age [y:d:h:m:s]: 01:009:22:12:53
Block: 992779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268095 RingCT/type: yes/0
Extra: 015256e89e45debb4787725a82b42164a4c725d6f11d1fd2c83c1f413e098e47a102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804779e6697fc49c3dd09289e3f087b4c2776fb06cd73a6204d40ab05d625b5c 0.600000000000 1453153 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": 992789, "vin": [ { "gen": { "height": 992779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804779e6697fc49c3dd09289e3f087b4c2776fb06cd73a6204d40ab05d625b5c" } } ], "extra": [ 1, 82, 86, 232, 158, 69, 222, 187, 71, 135, 114, 90, 130, 180, 33, 100, 164, 199, 37, 214, 241, 29, 31, 210, 200, 60, 31, 65, 62, 9, 142, 71, 161, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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