Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eba57666a8e15daa2ebaa167db47cffe5f345c20889706fb0dea4731a29537f

Tx prefix hash: b16292d45e83db5c2a2c6aa5f5f434fb90fe62cd0d6047958cc1bfe96274c019
Tx public key: 0094fa83393cd771d57e3462df200d7a76f0cb33825b952e8f84c47babf9014a
Timestamp: 1695504247 Timestamp [UCT]: 2023-09-23 21:24:07 Age [y:d:h:m:s]: 02:050:13:45:08
Block: 854672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555798 RingCT/type: yes/0
Extra: 010094fa83393cd771d57e3462df200d7a76f0cb33825b952e8f84c47babf9014a021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.903892791000 dcy

stealth address amount amount idx
00: 06e171e59aa1d078aecb5bbe09486251666cf00bd52245fec273d5582accb3d1 0.903892791000 1308658 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": 854682, "vin": [ { "gen": { "height": 854672 } } ], "vout": [ { "amount": 903892791, "target": { "key": "06e171e59aa1d078aecb5bbe09486251666cf00bd52245fec273d5582accb3d1" } } ], "extra": [ 1, 0, 148, 250, 131, 57, 60, 215, 113, 213, 126, 52, 98, 223, 32, 13, 122, 118, 240, 203, 51, 130, 91, 149, 46, 143, 132, 196, 123, 171, 249, 1, 74, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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