Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1cdd16fa1296701862accef10dcc01424970e16fda748ab728e980a607cf39

Tx prefix hash: b7c4549ca842967a4dffcc6dc16984e4c745ffb661a604addbbca13b122b61a6
Tx public key: 61e8bb36de1e6ff8b26acc08611872d960894c247413e74f1a5351e3672db22b
Timestamp: 1629100593 Timestamp [UCT]: 2021-08-16 07:56:33 Age [y:d:h:m:s]: 03:104:10:46:53
Block: 315174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 847849 RingCT/type: yes/0
Extra: 0161e8bb36de1e6ff8b26acc08611872d960894c247413e74f1a5351e3672db22b02110000002401f1e57f000000000000000000

1 output(s) for total of 55.425958963000 dcy

stealth address amount amount idx
00: 9b4ef2be68a35a8eef26f12f3422388f962cfc7a6caea059ae05b353c9b8afa0 55.425958963000 656031 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": 315184, "vin": [ { "gen": { "height": 315174 } } ], "vout": [ { "amount": 55425958963, "target": { "key": "9b4ef2be68a35a8eef26f12f3422388f962cfc7a6caea059ae05b353c9b8afa0" } } ], "extra": [ 1, 97, 232, 187, 54, 222, 30, 111, 248, 178, 106, 204, 8, 97, 24, 114, 217, 96, 137, 76, 36, 116, 19, 231, 79, 26, 83, 81, 227, 103, 45, 178, 43, 2, 17, 0, 0, 0, 36, 1, 241, 229, 127, 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