Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b55664d4e40d72bccb6b5a3f2cda4349234bc041d59f91f4fe35d39c8dd52c3e

Tx prefix hash: b6441c11c0503a1fe133a39fa47a5ccd04ecd75d12983f23e05605076645a3d7
Tx public key: 2043f1d36370069f772d1e7ca15dbff1927fdd68ae368d912223b32c72e5f1ac
Timestamp: 1681324181 Timestamp [UCT]: 2023-04-12 18:29:41 Age [y:d:h:m:s]: 02:009:14:36:02
Block: 737153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529018 RingCT/type: yes/0
Extra: 012043f1d36370069f772d1e7ca15dbff1927fdd68ae368d912223b32c72e5f1ac0211000000035029cbac000000000000000000

1 output(s) for total of 2.215676371000 dcy

stealth address amount amount idx
00: 9106d32a723c1498616b59ddc3fb6bb1cc7694d90a3db82f9a6a39bd2949b528 2.215676371000 1183670 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": 737163, "vin": [ { "gen": { "height": 737153 } } ], "vout": [ { "amount": 2215676371, "target": { "key": "9106d32a723c1498616b59ddc3fb6bb1cc7694d90a3db82f9a6a39bd2949b528" } } ], "extra": [ 1, 32, 67, 241, 211, 99, 112, 6, 159, 119, 45, 30, 124, 161, 93, 191, 241, 146, 127, 221, 104, 174, 54, 141, 145, 34, 35, 179, 44, 114, 229, 241, 172, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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