Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbde03cc7de9c343d2bae518584fd8d055436fcb3705d5841b7ed6e9d94ea332

Tx prefix hash: 9a8ef05b97e1ae1a0cf0697df6023aee5c7f103d2423700bb22c38032860ce37
Tx public key: 89d593cf8ebbdcf7cf81cfa7d7158479cb5876a4f8d58f6350f1017023aef825
Timestamp: 1625408337 Timestamp [UCT]: 2021-07-04 14:18:57 Age [y:d:h:m:s]: 03:315:11:11:31
Block: 288177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 994949 RingCT/type: yes/0
Extra: 0189d593cf8ebbdcf7cf81cfa7d7158479cb5876a4f8d58f6350f1017023aef825021100000060d142c209000000000000000000

1 output(s) for total of 68.101707931000 dcy

stealth address amount amount idx
00: b18afe00125db33de27bce592a48159aa51523db847170e5528bf2a888b45ed7 68.101707931000 603798 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": 288187, "vin": [ { "gen": { "height": 288177 } } ], "vout": [ { "amount": 68101707931, "target": { "key": "b18afe00125db33de27bce592a48159aa51523db847170e5528bf2a888b45ed7" } } ], "extra": [ 1, 137, 213, 147, 207, 142, 187, 220, 247, 207, 129, 207, 167, 215, 21, 132, 121, 203, 88, 118, 164, 248, 213, 143, 99, 80, 241, 1, 112, 35, 174, 248, 37, 2, 17, 0, 0, 0, 96, 209, 66, 194, 9, 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