Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea4449798d5f6e673f9eb5a1a91e4199aa45c887c851dbb8a244042c5b747b2c

Tx prefix hash: eb83ab613d7047f389ccec6f93cc79c88d44910fa9d126ca1d87535b7ada3125
Tx public key: 5bae8dfa6641af6ff413b4b25ce3706d87b4715e73767da7f9a1f8448df48bcd
Timestamp: 1707872143 Timestamp [UCT]: 2024-02-14 00:55:43 Age [y:d:h:m:s]: 01:049:07:14:52
Block: 957006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296268 RingCT/type: yes/0
Extra: 015bae8dfa6641af6ff413b4b25ce3706d87b4715e73767da7f9a1f8448df48bcd0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5cca47228d98b7377deaec5b0243fbe19259aebacdcf2b4c0242ebacfde4c6d 0.600000000000 1416320 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": 957016, "vin": [ { "gen": { "height": 957006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5cca47228d98b7377deaec5b0243fbe19259aebacdcf2b4c0242ebacfde4c6d" } } ], "extra": [ 1, 91, 174, 141, 250, 102, 65, 175, 111, 244, 19, 180, 178, 92, 227, 112, 109, 135, 180, 113, 94, 115, 118, 125, 167, 249, 161, 248, 68, 141, 244, 139, 205, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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