Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047c2b4fde135d54e9c43b9991accede7f05f8317ef9688b7cd38cd0eb97ef92

Tx prefix hash: c3dbe68f814848464ea6ff7373287ef50a2e84738c8903d92be6422f76835ece
Tx public key: 6e7582326e6f6babc0fd07195d6799bcd6d33590165dd2068f50c3aae19cde45
Timestamp: 1577735335 Timestamp [UCT]: 2019-12-30 19:48:55 Age [y:d:h:m:s]: 04:363:17:33:42
Block: 35291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149027 RingCT/type: yes/0
Extra: 016e7582326e6f6babc0fd07195d6799bcd6d33590165dd2068f50c3aae19cde4502110000002dac34bf9e000000000000000000

1 output(s) for total of 468.885844288000 dcy

stealth address amount amount idx
00: 8b95b4d8bc7a1934f68e71d58bf53a8d083774bc085a476ffaa57b9dfa6a79b1 468.885844288000 59437 of 0

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": 35301, "vin": [ { "gen": { "height": 35291 } } ], "vout": [ { "amount": 468885844288, "target": { "key": "8b95b4d8bc7a1934f68e71d58bf53a8d083774bc085a476ffaa57b9dfa6a79b1" } } ], "extra": [ 1, 110, 117, 130, 50, 110, 111, 107, 171, 192, 253, 7, 25, 93, 103, 153, 188, 214, 211, 53, 144, 22, 93, 210, 6, 143, 80, 195, 170, 225, 156, 222, 69, 2, 17, 0, 0, 0, 45, 172, 52, 191, 158, 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