Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74b4da5a527645a6aafecd19bad5b5ed8be31a20281d2a48352dc4cbd847977

Tx prefix hash: 98051ee29ac893cedfd8a777e06b9e95e12b0b27debe4ead90b71eb182c185c9
Tx public key: 74bff4d1a85acea1141316814fec9ecbcd85c5b8b7bc7e6bb67d7733ca614dce
Timestamp: 1722835208 Timestamp [UCT]: 2024-08-05 05:20:08 Age [y:d:h:m:s]: 00:172:00:04:36
Block: 1081054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123010 RingCT/type: yes/0
Extra: 0174bff4d1a85acea1141316814fec9ecbcd85c5b8b7bc7e6bb67d7733ca614dce021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 253d3d516fa3f856c0f710e4bd03e35d8ff064f6ef698cf639d14daf031780c1 0.600000000000 1554651 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": 1081064, "vin": [ { "gen": { "height": 1081054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253d3d516fa3f856c0f710e4bd03e35d8ff064f6ef698cf639d14daf031780c1" } } ], "extra": [ 1, 116, 191, 244, 209, 168, 90, 206, 161, 20, 19, 22, 129, 79, 236, 158, 203, 205, 133, 197, 184, 183, 188, 126, 107, 182, 125, 119, 51, 202, 97, 77, 206, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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