Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df1bb024ed9772ea2a28b935d20f21dba9ad08e00f3ebdac14e2079c20eb0314

Tx prefix hash: de5b4201297090b2b9a49d807e4a710695c4dc9e6c5fc32c120312bbe4bd6b45
Tx public key: 0de221e95ccc2e8ce7b5a8b47f37d70dcc88f2591dbcf8f8a6a9cb97438551b1
Timestamp: 1701723103 Timestamp [UCT]: 2023-12-04 20:51:43 Age [y:d:h:m:s]: 01:342:08:10:27
Block: 906029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503537 RingCT/type: yes/0
Extra: 010de221e95ccc2e8ce7b5a8b47f37d70dcc88f2591dbcf8f8a6a9cb97438551b102110000000333af99f4000000000000000000

1 output(s) for total of 0.610871392000 dcy

stealth address amount amount idx
00: 3ddff6491082e8c056313ffc5dd6db6bcd857b4e0eadf6c9b154df24d373b213 0.610871392000 1362950 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": 906039, "vin": [ { "gen": { "height": 906029 } } ], "vout": [ { "amount": 610871392, "target": { "key": "3ddff6491082e8c056313ffc5dd6db6bcd857b4e0eadf6c9b154df24d373b213" } } ], "extra": [ 1, 13, 226, 33, 233, 92, 204, 46, 140, 231, 181, 168, 180, 127, 55, 215, 13, 204, 136, 242, 89, 29, 188, 248, 248, 166, 169, 203, 151, 67, 133, 81, 177, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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